Upgrading Components

If you use work groups, configure the runtime user validation after upgrading from Tidal Automation versions older than 6.2.2.

Note: The TA Master and Client Manager need to be on the SAME release to ensure compatibility and functionality. The TA Master running on Windows no longer uses database aliases as created by the Database Alias utility to connect to an alternate database. Instead, the database connection information used by the Master in 6.1 and later is stored in the master.props file in the config directory where the Master files are installed. The JdbcURL line in the master.props file is used to specify the type of database, the database server location, and the port number used to connect to the database server. See Configuring the Master Parameters (master.props) for more information.

Upgrade Prerequisites

  • Take a backup of your database and data before upgrading.

  • Ensure Java 17 is installed as the Tidal platform is built to run with this version.

  • Ensure your system meets the minimum hardware and software requirements for the latest version. The hardware and software requirements may have changed from the last version.

  • Ensure to use the Oracle system user to upgrade Tidal Automation on the Oracle DB.

Post Upgrade Requirements

Note: To ensure the system works properly, run these commands again after finishing the installation process.

Note: If upgrading from Tidal Automation versions before Tidal Automation 6.5.9, ensure you recompile all future schedules after the upgrade.

Password Re-encryption

Note: This step is necessary if you're upgrading to Tidal Automation 2024.3 because previous versions used a different method for encrypting passwords. By running these commands, you'll update to the new encryption scheme, ensuring that all systems work smoothly.

Note: If you are using Tidal Automation Client Manager versions older than 2024.3.20 and experiencing issues after upgrading and re-encrypting passwords, check the user-auth.xml file. If you see the <?xml version="1.0" encoding="UTF-8" standalone="no"?> tag, remove it.

To ensure the system operates correctly, re-run these commands after completing the installation process:

  • cm reencryptcmpwd clientmgr.props
  • cm reencryptcmpwd tes-6.5.dsp (production.dsp)

    Note: tes-6.5.dsp is the default DSP file.

  • tesm reencryptpwd master.props

Password Re-encryption for Windows

Follow this instruction for the Client Manager:

  1. Open the command prompt, CMD, as the Administrator.

  2. Navigate to the script folder using this command:

    cd C:\Program Files\TIDAL\ClientManager\script

  3. Run these commands for the Client Manager:

    • cm reencryptcmpwd clientmgr.props
    • cm reencryptcmpwd tes-6.5.dsp (production.dsp)

Follow this instruction for the Master:

  1. Open the command prompt, CMD, as the Administrator.

  2. Navigate to the script folder using this command:

    C:\Program Files\TIDAL\Scheduler\Master\script

  3. Run this command for Master:

    tesm reencryptpwd master.props

Password Re-encryption for Linux

Follow this instruction for the Master:

  1. Navigate to the installed TIDAL folder, and then to master/bin.

  2. Enter this command:

    sudo ./tesm reencryptpwd master.props

Follow this instruction for the Client Manager:

  1. Navigate to the installed TIDAL folder, and then to ClientManager/bin.

  2. Enter these commands:

    • sudo ./cm reencryptcmpwd clientmgr.props
    • sudo ./cm reencryptcmpwd tes-6.5.dsp (production.dsp)